Known Issues
Following is a list of known issues in erwin Mart Portaland erwin ER360:
erwin Mart Portal
Issue |
Description |
---|---|
Error msg is displayed when the DI model is opened in erwin DM - Checkout Enabled |
When you open a model imported from erwin Data Intelligence (erwin DI) via DM Connect for DI, Click OK on the error message to proceed. |
erwin Mart - Cassandra: Exporting Cassandra model into DI displays the Column Definition value in Column Comments |
The export of a Cassandra model into erwin DI using DM connect for DI is displaying After the export, the Column Definition value is displayed in the Column Comments. |
erwin Mart - Azure SQL: The Settings and DI Configuration tabs do not |
The Settings and DI Configuration tabs do not display user password in the erwin Mart Portal |
erwin Data Modeler cannot Connect to erwin Mart Portal on |
erwin Data Modeler (DM) cannot connect to the erwin Mart Portal (MS) on an This happens because the client application version is different from the To counter this issue, do the following:
|
Mart Portal Name in Korean |
Suppose that you provide the Mart Portal machine name in the Korean language If you try to connect to the Mart from erwin DM and you provide the Korean language name for Server Name, the following message appears:
If you try to log in to erwin Mart Portal by using the Korean language name, it does not display. |
Error While Creating a Profile Using Special Characters in Mart Portal |
When you create a profile in Mart Portal using special characters such as Illegal Group or 500 The call failed on the server; see server log for details or String index out of Range:1 To avoid this error, create a profile without using the special characters. |
Generating Reports with Korean Characters in User Name |
Suppose that you have initialized a Mart with a user name that |
DM Connect for DI: Valid values are not exported, if the name |
When you use the validation rules, valid values are not exported to DI |
Variance in NSM Reports in erwin DM |
Edit NSM option and few variances are noticed after running the report |
DM-DI Connect: Validation Rule Valid Value properties are not |
Validation Rule of Valid Value property values are not displaying in a |
erwin ER360
Issue |
Description |
---|---|
Metadata Browser-Representation of Neo4j nodes on physical side of ER360's ER diagram differs from the one represented in DM. | Representation of Neo4j nodes on physical side of ER360's ER diagram differs from the one represented in DM. |
Metadata-The Subtype symbols doesn't match in ER 360 when compared to Erwin DM. Subtype allign issue | The subtype relationship display of ER360 is not matching with erwin DM. Instead of subtype symbol the clear line is shown in ER 360. The path of subtype is also different |
Metadata browser- Data types are not getting changed after applying the DSM in Dataflow impact analysis |
After applying the DSM the data types are not getting changed from logical to physical |
Copyright © 2025 Quest Software, Inc. |